[DEE] Add hardware thresholds to determine if a MDEEStripHit was a NearestNeighbor or not - #190

Currently, MSubModuleChargeTransport generates up to three MDEEStripHits for each the HV and LV side, namely for the strip in which the original simulated hit took place, and the two adjacent strips. This part of the DEE does not know if a MDEEStripHit will end up triggering, becoming a NN strip hit, or not being read out at all.

In MSubModuleStripReadout, we apply what I call a "hardware threshold", which is a strip-specific energy threshold in ADC units to determine if a strip triggered or not. The current logic is:

• If a MDEEStripHit exceeds its hardware threshold, then both neighbors should exist and be read out
• If a MDEEStripHit did not exceed its hardware threshold, it will only be read out (as a NN strip), if at least ONE of the adjacent strips exceeded its hardware threshold.

For this, I had to

• add a m_IsNearestNeighbor flag to MDEEStripHit
• write code to read a hardware threshold file (in MModuleEnergyCalibration), and code to apply it (in MSubModuleStripReadout)
• write a loop to iterate through all MDEEStripHits after the charge-transport simulations to:
  1. find all TriggeredStrips (above hardware threshold), all NeighborCandidateStrips (neighbors of strips above hardware threshold), all DeadStrips (without energy calibration)
  2. remove all strips below hardware threshold that do not have a neighboring TriggeredStrip
  3. create empty (energy = 0, small timing) MDEEStripHits for all NeighborCandidateStrips that were not created during MSubModuleChargeTransport

Here is a sketch to illustrate the logic behind the final loop: